Repository navigation
docs: document roles on specific projects - #8450
Draft
mintlify[bot] wants to merge 5 commits into
Draft
mintlify[bot] wants to merge 5 commits into
mintlify[bot] wants to merge 5 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
ethanpalm
approved these changes
Nov 13, 2026
ethanpalm
left a comment
ethanpalm
left a comment
Collaborator
There was a problem hiding this comment.
just a few small changes
| 1. Navigate to the [Members](https://app.mintlify.com/settings/organization/members) page of your dashboard. | ||
| 2. In the member's row, select a new role from the **Role** dropdown. The change saves immediately. | ||
|
|
||
| If your organization can give members [roles on specific projects](/dashboard/roles#roles-on-specific-projects), you change roles from the member's actions menu instead: select **Edit role**. |
Collaborator
There was a problem hiding this comment.
Suggested change
| If your organization can give members [roles on specific projects](/dashboard/roles#roles-on-specific-projects), you change roles from the member's actions menu instead: select **Edit role**. | |
| If your organization can give members [roles on specific projects](/dashboard/roles#roles-on-specific-projects), you change roles from the member's actions menu instead. Select **Edit role** for the member whose role you want to adjust. |
Contributor
Author
There was a problem hiding this comment.
Applied, so it's two sentences now.
|
|
||
| ## Roles on specific projects | ||
|
|
||
| If your organization has more than one project, you can give a member a higher role on specific projects than their organization role. For example, a viewer can be an editor on one project. A project role only raises access on that project. It never lowers access and doesn't apply to your other projects. |
Collaborator
There was a problem hiding this comment.
Suggested change
| If your organization has more than one project, you can give a member a higher role on specific projects than their organization role. For example, a viewer can be an editor on one project. A project role only raises access on that project. It never lowers access and doesn't apply to your other projects. | |
| If your organization has more than one project, you can give a member a role with more access on specific projects than their organization role. For example, a viewer in your organization can be an editor on one project. A project role only raises access on that project. It never lowers access and doesn't apply to your other projects. |
Contributor
Author
There was a problem hiding this comment.
Applied: "a role with more access" and "a viewer in your organization".
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents giving a member a different role on specific projects than their organization role, from the Edit access and permissions drawer on the Members page: a higher role, or No access to block them from a project. Includes matching notes on the Members page and the team instructions topic.
Based on merged dashboard and server changes that add per-project roles and the No access role. Draft because this may not be generally available yet; mark ready once it rolls out.